<?xml version="1.0"?>
<!-- 
	
	This file is not used, but is a guide as to how to best use assemblies
	to load in Eonicweb and its associated assemblies in a local site.
	
	The idea is to use the GAC (and its mappings where possible) and make adjustments 
	if needing to debug a specific local site.
	
	BIN FOLDER:
	===========
	
	The only thing REQUIRED in a BIN folder is EonicWebv4_0.dll, whether it be copied there or placed
	there by a debug project.
	
	The reason for this is that the SectionHandler across the machine does not specify a version number (or a fully qualified name)
	which means that it can't load the SectionHandler from the GAC.
	
	<section name="messagingProviders" type="Eonic.ProviderSectionHandler, EonicWebV4_0" restartOnExternalChanges="false"/>

	If we add a version number to this, then yes, we would not need local BIN, but then versions not mapped in the GAC would fall over.
	
-->
<configuration>

	<eonic>
		<messagingProviders>
			<providers>
				<!-- The provider should have a version that is picked up by the GAC, either by direct reference or mapping -->
				<add name="CampaignMonitorProvider" type="CampaignMonitorEonicWebIntegration, Version=1.0.1.0, Culture=neutral, PublicKeyToken=a33375f49b09b5d7"/>
			</providers>
		</messagingProviders>
	</eonic>
	<system.web>
		<compilation defaultLanguage="vb" debug="true" urlLinePragmas="true">
			<assemblies>
				<!-- Add all the assemblies that you are not building the project against -->
				<!-- i.e. If you are building the site against the EonicWeb project then omit that -->
				<add assembly="EonicWebV5, Version=5.0.0.0, Culture=neutral, PublicKeyToken=0e5e11efc3341916"/>
				<add assembly="Eonic.Tools, Version=5.0.0.0, Culture=neutral, PublicKeyToken=2030ce1af675e93f"/>
				<add assembly="CampaignMonitorEonicWebIntegration, Version=1.0.1.0, Culture=neutral, PublicKeyToken=a33375f49b09b5d7"/>
				
			</assemblies>
		</compilation>
	</system.web>
	<!-- 
		If you are building the site against a new version of an assembly, then you need to update the mapping 
		locally to point to the version that you are building, because any dependent assemblies in the GAC
		will be looking for a different version of that assembly. 
		
		e.g. 
			EonicWebV4_0 4.1.1.89 and CampaignMonitor 1.0.1.0 are in the GAC
			You are developing EonicWebV4_0 4.1.1.91, but not CampaignMonitor.
			CampaignMonitor will be looking for EonicWeb 4.1.1.89, which will cause a conflict in 
			any references to EonicWeb, so you need to update the mappings for EonicWeb, as below.
	-->
	<runtime>
		<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
			<dependentAssembly>
				<assemblyIdentity name="EonicWebV5" publicKeyToken="0e5e11efc3341916"/>
				<bindingRedirect oldVersion="5.0.0.0-5.0.1.9" newVersion="5.0.1.9"/>
			</dependentAssembly>
			<dependentAssembly>
				<assemblyIdentity name="Eonic.Tools" publicKeyToken="0e5e11efc3341916"/>
				<bindingRedirect oldVersion="5.0.0.0-5.0.1.9" newVersion="5.0.1.9"/>
			</dependentAssembly>
		</assemblyBinding>
	</runtime>


</configuration>
